Some Tips, Tricks, and Workarounds for IBM DOS 4.0
(From the August 29 issue of InfoWorld.)

     In using IBM DOS 4.0 over the past several weeks, I've run into a
few problems and come up with a few solutions.  In most cases the
solutions are pretty simple - but not obvious.


     Problem - Video conflicts while running terminate-and-stay-resident
programs (TSR's) and DOS 4.0's DOS shell in graphics mode.

     Solution - Put DOS 4.0's DOS shell into text mode.  To do this, you
must edit the file 'dosshell.bat' and change the video argument.  Here's
how you can do that:  Find the line with the command SHELLC and then
enter the argument "/TEXT".

     For instance, a correct line might include a number of arguments,
such as @SHELLC/.../DOS/MENU/MUL.../TEXT.  Alternative choices with
different resolutions and color paletts are /CO1,/CO2, and /CO3.


     Problem - MicroSoft Windows/386 won't work.

     Solution - You need to use a newer release of MicroSoft
Windows/386, version 2.10.  To work with DOS 4.0, the version must be
dated on or after July 1, 1988.  Call MicroSoft.


     Problem - Disk utilities, such as Norton Utilities, Mac Utilities,
Golden Bow, etc., don't work with IBM DOS 4.0.

     Solution - Call the vendor for a new version.  IBM DOS 4.0 uses a
different file allocation table (FAT), so disk optimizers and utilities
designed for earlier versions of DOS will not work.  Most vendors have
either already released or are currently working on updates that will
work with DOS 4.0.


     Problem - Lotus Metro doesn't work under DOS 4.0.

     Solution - The current version simply doesn't work.  Switch to
another program or wait for an update.


     Problem - Expanded memory options don't work with third-party
memory boards.

     Solution - Use the Expanded Memory Specification software supplied
with the board rather than the EMS software supplied with DOS 4.0.  The
EMS software supplied with DOS 4.0 is specific to IBM hardware.


     Problem - IBM DOS 4.0 will not install on a hard disk that already
has another vendors version of MS-DOS 3.x installed.

     Solution - Edit the boot sector of the hard disk drive (using a
program such as the Norton Utilities) to match the DOS 4.0 floppy.


     Problem - Expanded Memory causes conflicts.

     Solution - Do not use the "/x" command with Buffers, Fastopen,
Vdisk, etc.  This command lets IBM DOS 4.0 store some system information
in Expanded Memory, but it can cause conflicts with other Expanded
Memory software, which can produce potentially disastrous results.